Repository navigation
ci: validate dependency updates against live main - #13
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pin the reviewed dependency merge action to
05bc24e1b7dc3374919a35093e53b3dc66d6ab24(zixcel/zixcel-repository-security#33). Resolve the current main Git ref instead of the historical PR base SHA, preventing stale dependency proposals from being treated as current. Fourteen policy/orchestration regression tests, strict TypeScript and all owner CI passed for the shared action. Only this immutable reference changes; activation, permissions, required checks, publication and deployments are unchanged. This completes the automatic maintenance requested by the owner.